System and method for automatic call scheduling

ABSTRACT

A computer system for connecting a user to a scheduled call, including a processor in communication with non-volatile memory and code for receiving a user phone number where the user may be contacted and information allowing access to the user&#39;s calendar or email, code for accessing the user&#39;s calendar or email and identifying the scheduled call in the user&#39;s calendar or email, the scheduled call having information including at least a scheduled call number and a scheduled call time, code for placing a call to the scheduled call number before the scheduled call time, code for placing a call to the user at the user phone number before the scheduled call time, code for confirming the user has answered the call to the user, and code for connecting the call to the user to the call to the scheduled call number.

BACKGROUND OF THE INVENTION

Business people and other busy individuals often schedule multiple phonecalls throughout a day and may encounter difficulty participating ineach scheduled call. For example, a call may continue past a given timeslot and may “run over” into a second call, thereby causing the user tobe late for the second call. Or, an incoming call or other exigent eventmay cause the user to forget a call completely. For these and otherreasons, there is a need for a system and method that will connect theuser with a scheduled call. In one aspect, the system may dial into andconnect with a scheduled call, dial the user, and connect with user withthe scheduled call.

SUMMARY OF THE INVENTION

A computer system for connecting a user to a scheduled call, including aprocessor in communication with non-volatile memory, the non-volatilememory including code for receiving a user phone number where the usermay be contacted and information allowing access to the user's calendaror email; code for accessing the user's calendar or email andidentifying the scheduled call in the user's calendar or email, thescheduled call having information including at least a scheduled callnumber and a scheduled call time; code for placing a call to thescheduled call number before the scheduled call time; code for placing acall to the user at the user phone number before the scheduled calltime; code for confirming the user has answered the call to the user;and code for connecting the call to the user to the call to thescheduled call number.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings presented herein are for the purposes of illustration, theinvention is not limited to the precise arrangements andinstrumentalities shown.

FIG. 1 is a view of the system according to an aspect of the presentdisclosure.

FIG. 2 is a view of the API system with viral behavior according to anaspect of the present disclosure.

FIG. 3 is a flowchart of activity from the user's entry into the serviceaccording to an aspect of present disclosure.

FIG. 4 is a flowchart of activity of the viral API to acquire usersaccording to an aspect of present disclosure.

FIG. 5 is a flowchart of activity from the user's entry into the serviceapplication according to an aspect of present disclosure.

FIG. 6 is a diagram displaying a general purpose computer on which thesystem and method of the present disclosure may be implemented accordingto an aspect of present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

As shown in FIG. 1, the System 1 may be triggered once the initial User2 grants the System 1 access to the cloud-based Calendar 3 of User 2through the use of an API 33. API 33 may be attached to or embeddedwithin System 1 and may have viral components. Once this occurs, theSystem 1 scans the Calendar 3 for Events 4. The User 2 also provides theSystem 1 with a User Phone Number 22 at which the User 2 can becontacted. At this time, User 2 can also provide the System 1 withconference call or telecom Provider 6 and PIN 7 if they manage a Bridge8.

In one aspect of present disclosure, User 2 may install SystemApplication 38 onto Smartphone 36. In this aspect, if User 2 hasCalendar 3 linked with Smartphone 36, then Calendar 3 is capable oflinking to Application 38. Once connected, Application 38 may sendNotification 37 to User 2 through System 1 to Smartphone 36, alertingUser 2 that Call 14 is starting. When Notification 37 is pushed, User 2is directed to Application 38, where they may be presented with Link 39which once clicked, launches the phone dialer using the constructed dialstring. The System 1 acknowledges that the call was initiated throughthe Application 38, and creates DTMF Tones 25 compatible specificallyfor Smartphone 36. Once acceptable DTMF Tones 25 are placed into the IVR24, then User Phone Number 22 is placed into Smart Devices networkcarrier (not shown) and dialed autoratically along with Scanned PhoneNumber 5 to initiate Call 14 within Event 4.

When the System 1 detects an Event 4, the System 1 may attach a “SystemConfirmed” Notification 34 to the Event 4's title within the Calendar 3.The System 1 scans Event 4 for Attendee Phone Numbers 5, Providers 6,PINs 7 and Email Addresses 17 of additional call Attendees 16 and crossreferences the results within the System Database's 9 List of Providers10 to confirm matches if necessary. System 1 also seeks new informationor other flags that may be Calls 14, i.e., phone numbers and/or VoIPservices and corresponding usernames, e.g., Skype.

If one or more required items, e.g., Attendee Phone Number 5, PIN 7, andProvider 6 are missing, or are not recognized by the System Database 9,then the Event 4 may be filtered through an Unknown Calls Queue 11 thatmay be continually monitored by Human Agent 12 who may manually edit andadjust the Events 4. Human Agent 12 may be informed every time a newEvent 4 is entered into the Unknown Calls Queue 11. Once Human Agent 12finds the required information, they may manually edit the Call 14 sothat pertinent call information matches the information in the List ofProviders 10, then the call may be placed in a Scheduled Call Queue 13.

If some of the required items are not found by the Human Agent 12 (e.g.Attendee Phone Number 5, PIN 7) and/or Human Agent 12 confirms that thecalendar Event 4 does not actually include a Call 14, then the calendarEvent 4 may be placed in a Discarded Call Queue 15, but retained in theSystem Database 9 for future analytics.

FIG. 2 shows a view of the API 33. If System 1 recognizes additionalEmail Address(es) 17 of Attendee(s) 16 within Event 4, then API 33 maysend Email 18 to additional Attendee(s) 16. Within Email 18 is Link 19,prompting the Attendee(s) 16 to sample the service by clicking on theLink 19. Once they have clicked on the Link 19, Attendee(s) 16 aredirected to Landing Page 20 where they are offered to input theirAttendee Phone Number 5 into Input 21. From there the Attendee(s) 16 aredirected to Landing Page 32 confirming that they will be connected toCall 14 on time.

Before the time of the Call 14, the User 2 and those Attendee(s) 16 whoprovided the System 1 with their Attendee Phone Numbers 5 are placedinto Softswitch 23. The Softswitch 23 is triggered to dial and bridgethe User 2 and Attendee(s) 16 to the Provider 6, if necessary, at somedesignated time before the Call 14 is scheduled to begin and thenconnects them. If said Provider 6 requires a PIN 7, then the System 1generates an IVR 24 that simulates the DTMF Tones 25 needed to bridgethe User 2 to the Provider 7. DTMF Tones 25 may include PIN 7 plus anyadditional tones needed to confirm passcode entry, or to navigatepotential audio menus. If the System 1 generates the IVR 24successfully, then User 2 and Attendee(s) 16 will be placed into theirscheduled Call 14 promptly on time.

Once Call 14 is finished, and/or Attendee(s) 16 have stayed on the Call14 longer than some predetermined threshold, thus exhausting one of theAttendee(s) 16 Free Trial Usage(s) 31 then the Attendee(s) 16 is sentEmail 26 by System 1. Within Email 26 is Link 27 offering Attendee(s) 16a link to try the service. If Link 27 is clicked on, then Attendee(s) 16are directed to Landing Page 28, providing Input 29 to sign up for theservice. Once all pertinent information is successfully placed intoInput 29, then Attendee(s) 16 become New User(s) 30.

If Attendee(s) 16 do not stay on Call 14 longer than the predeterminedthreshold, then Attendee(s) 16 does not exhaust one of their Free TrialUsage(s) 31. If Attendee(s) 16 does exhaust one of their Free TrialUsage(s) 31, and does not click on Link 27 within Email 26, then System1 acknowledges that Attendee(s) 16 has exhausted one of their Free TrialUsage(s) 31. Once Attendee(s) 16 has exhausted all of their Free TrialUsage(s) 31 then they are directed to Landing Page 35, informing thatthey have exhausted all of their Free Trial Usage(s) 31. Within LandingPage 35 is Link 40, offering Attendee(s) 16 the option to sign up forthe service. If Link 40 is clicked, then Attendee(s) 16 are directed toLanding Page 28, where they can place all pertinent information withinInput 29 to sign up for the service. Once all pertinent information issuccessfully placed into Input 29, then Attendee(s) 16 become NewUser(s) 30.

FIG. 3 is a flowchart of activity from the user's entry into the serviceand completion of the service according to an aspect of presentdisclosure. At Step 102, the User 2 provides System 1 with access to theCalendar 3 and/or Email Messages 41, which may be located on the user'scomputer or located remotely, for example, accessible in a networkand/or the cloud. At Step 104, the User 2 provides a User Phone Number22 where the User 2 wishes to receive calls. User 2 may provide theSystem 1 with a conference call number or telecom Provider 6 and PIN 7whereby User 2 may be contacted. If the Call 14, between User 2 andAttendee(s) 16, is not a direct call from Attendee Phone Number 5 toUser Phone Number 22, then an IVR 24 and DTMF Tones 25 may be used bySystem 1 to automate the process of bridging calls within a ConferenceBridge 8. At Step 106, User adds an Event 4 to Calendar 3 or receives anEmail Message 41 containing call information, this information may beupdated automatically. Updates may include synchronizing with User 2'scalendar Events 4 or Email Messages 41 and may occur at predeterminedtimes or intervals or when an Event 4 is created or changes. In oneexample, when an applicable Event 4 is added to the User 2's Calendar 3,the System 1 collects Event 4 data, then may attach a Notification 34 tothe User 2's Event 4, e.g., appending “System Confirmed” to the title,in Calendar 3. System 1 may attach Notification 34 at the time ofcollection and/or after the Event 4 is fully or partially processed bySystem 1.

At Step 110, the System 1 scans the user's calendar Events 4 forinformation relating to upcoming Calls 14, such as User Phone Numbers22, passcodes or PINs 7 for conference calls, and identity of telecomProviders 6 and places the data in System Database 9. The System 1 alsoscans for references to call-related software, such as Skype andcorresponding user names as well as Email Addresses 17 of Attendees 16.In a similar manner, System 1 may scan Email Messages 41 for thosecontaining Events 4 or information regarding upcoming Calls 14. If theSystem 1 finds such information at Step 112, then at Step 114, theSystem 1 determines whether the information matches data, such asAttendee Phone Number 5, passcode or PIN 7, and/or Provider 6 stored inthe System Database 9. If matches are found, that data may have beenused to connect a prior call and generate a prior IVR 24, which theSystem 1 may now use to connect User 2 to the current Call 14. Certaininformation may be determined to be required, e.g., based on experiencewith past calls, to create a call Event 4, which may include AttendeePhone Number 5, passcode or PIN 7, or Provider 6. For example, when theCall 14 is a direct call between two individuals, then the informationneeded may be an Attendee Phone Number 5. If the Call 14 is bridging anindividual into a conference bridge, then the conference bridge phonenumber and optional PIN or passcode may be required to bridge the callsuccessfully. In one aspect, the System 1 may determine that informationregarding Event 4 is similar to or the same as existing informationstored in Database 9. For example, Event 4 may be associated with orheld by a vendor for which information is stored in Database 9. If theSystem 1 determines that additional steps are needed to connect, forexample, requiring the caller to state their name or press certainbuttons, then, as described below, the System 1 may generate audio usingtext-to-voice or DTMF tones to navigate those additional steps.

If one or more required items are missing or are not recognized by theSystem Database 9 or upon an error condition, (No, Step 112) then atStep 120 the Event 4 may be sent to an Unknown Calls Database 11 thatmay be monitored by a Human Agent 12. Human Agent 12 then finds theappropriate information to schedule the Call 14 in Step 122. Byretrieving said data within Event 4 and System Database 9 (Yes, Step122), Human Agent 12 may ensure Call 14 will be bridged correctly inStep 126, e.g., by manually editing information. If the Human Agent 12does not find any of the pertinent information and/or determines thatEvent 4 is not a Call 14 (No, Step 122), then at Step 124 the HumanAgent 12 may discard the Call 14 or may take additional steps such ascontacting the User 2.

System 1 finds Email Address(es) 17 of Attendee(s) 16 (Yes, Step 112).Then Attendee Phone Number 5, passcode or PIN 7 and Provider 6 found arecross-referenced to find matches in System Database 9 in Step 114. InStep 116 these Email Addresse(s) 17, found during Step 110 are sentEmail(s) 18 through the System 1 API 33 to capture New User(s) 30.

Once all pertinent data is matched from System Database 9 and Event 4(Yes, Step 118 or after Step 126), the Call 14 is placed in ScheduledCall Queue 13 at Step 128. At Step 130, the Call 14 is placed into aSoftswitch 23 which is triggered at the time of the Event 4, ortriggered at a time prior to the Call 14, based on the conference callprovider and stored knowledge of Provider 6, to connect the User 2 tothe selected Provider 6.

User 2 is then contacted by System 1 at Step 132. If the Provider 6 doesnot require input, e.g., PIN 7 at Step 134, then the System 1 bridgesthe call successfully at Step 138 If the Provider 6 requires a PIN 7,then at Step 136 System 1 generates an IVR 24, using PIN 7, thatsimulates the DTMF Tones 25 required to bridge the Call 14 successfully.System 1 may contact User 2, to join User 2 to Call 14. For example,System 1 may place a call to User 2 on Smartphone 36, whereupon User 2may be prompted to join Call 14, such as by pressing a specific key ontheir phone. In other aspects, System 1 may contact User 2 via email orother messaging platform, such as SMS or MMS, and provide instructionsregarding how to join or the ability to join Call 14. As describedbelow, in other aspects System 1 may communicate with an applicationresident on Smartphone 36 to facilitate User 2 joining Call 14.

At Step 138, User 2 joins the Call 14, then Call 14 is bridgedsuccessfully. User 2 may also be prompted in other ways to join the Call14, such as voice recognition. If the conference call software requiresthe user to state their name before connecting to the call, User 2 maybe prompted to provide System 1 with a recording stating the User'sname, or System 1 may convert User 2's name using text-to-speechsoftware. This recording may be stored in the Database 9, retrieved andplaced into the IVR 24 at the time of the Call 14. Alternatively, System1 may attempt to skip the voice recognition within the IVR 24 by placinga pause or sound into the DTMF Tones 25. If IVR 24 is not approved, thenHuman Agent 12 may manually record and provide the name of the User 2during the IVR process, ensuring User 2 is automatically bridged intotheir scheduled Call 14. If the process requires speech, and thebridging is not handled by software, but rather a human, then the HumanAgent 12 may be placed into the call, provides the name of the User 2manually, and once connected, manually connects User 2 to the scheduledCall 14.

FIG. 4 details the processes involved in capturing additional users forthe service using an API 33 and is labeled as Step 116. This API 33 maybe a viral rnechaism triggered as a result of System 1 finding all dataneeded to set up the Call 14, including the Email Address(es) 17 ofAttendee(s) 16 in Step 112. At Step 202 when System 1 sends an Email 18to the Email Address(es) 17 of Attendee(s) 16 offering a Link 19 to FreeTrial Usage 31. If this is one of the first predetermined number of atotal predetermined number of usages granted by the System 1, Attendee16 clicks on Link 19 without exhausting Free Trial Usages 31 at Step204, then they are sent to Landing Page 20 in Step 206, which directsAttendee 16 to put their Attendee Phone Number 5 into Input 21. WhenAttendee(s) 16 puts their Attendee Phone Number(s) 5 into Input 21 atStep 208, then System 1 sends Attendee(s) 16 to Landing Page 32 at Step210 confirming that the Attendee(s) 16 will be called on time. At Step212 Attendee(s) 16 is dialed into scheduled Call 14, thus using one ofAttendee 16's Free Trial Usages 31. At Step 214, if Attendee(s) 16 doesnot stay connected to the Call 14 longer than the threshold required touse Free Trial Usage 31, then there is no further action taken by System1 in Step 216. If Attendee(s) 16 stays connected to the Call 14 longerthan the threshold required to use Free Trial Usage 31 during Step 214,then System 1 sends Attendee(s) 16 follow-up Email 26 during Step 218presenting a Link 27 to join the service by allowing Attendee(s) 16 togo through the sign-up process.

If the Attendee(s) 16 do not click on the Link 2 during Step 220 and donot complete the sign-up process to join the service, then in Step 228the System 1 records that the Attendee(s) 16 has used one of theirallotted Free Trial Usages 31. If the Attendee(s) 16 has exhausted theirallotted Free Trial Usages 31 at Step 230, then in Step 232 Attendee(s)16 are sent to Landing Page 35 informing the Attendee(s) 16 that theyhave exceeded their number of Free Trial Usage(s) 31, Attendee(s) 16 arealso offered Link 40 to sign up for the service. If the Attendee(s) 16have not exhausted their predetermined number of Free Trial Usages 31,and they do not click on Link 40, then the Attendee(s) 16 may be able torepeat Step 116 and use the service over and over until they haveexhausted their Free Usage Trials 31.

If the Attendee(s) 16 click on the Link 27 in Step 214 or Link 40 inStep 220 to join the service, then the System 1 sends Attendee(s) 16 toLanding Page 28 in Step 218 offering Input 29 to sign up for theservice. Once again, if the Attendee(s) 16 does not put in theirinformation into Input 29, then System 1 records that the Attendee(s) 16has used one of their allotted Free Usage Trials 31 in Step 216. If theAttendee(s) 16 do put their information into Input 29, then theAttendee(s) 16 successfully signs up for the service in Step 222,officially becoming New User 30.

As shown, FIG. 5 is a flowchart of activity from the user's entry intothe service using a smartphone application according to an aspect ofpresent disclosure. At Step 302, the User 2 launches the serviceApplication 38 on their Smartphone 36. At Step 304, User 2 connectsCalendar 3, if already synced to User 2's Smartphone 36, to Application38 to provide access to the user's Calendar 3 or email messages, and theEvent(s) 4 located within. Once Calendar 3 or email messages are syncedto System 1 and Application 38, then Application 38 is then connected toSystem 1 at Step 306. At Step 308, the User 2 provides a User PhoneNumber 22 where the User 2 wishes to receive calls. User 2 may alsoprovide the System 1 with a conference call or telecom Provider 6 andPIN 7. If the call is not a direct call from Attendee Phone Number 5 toUser Phone Number 22, then an IVR 24 and DTMF Tones 25 are used toautomate the process of bridging calls within a Conference Bridge 8. AtStep 310, User adds an Event 4 to their Calendar 3 and may be updatedautomatically. Updates may include synchronizing with User 2's calendarEvents 4 or Email Messages 41 and may occur at predetermined times orintervals or when an Event 4 is created or changes. When an Event 4 isadded to the User 2's Calendar 3, the System 1 collects Event 4 data,then may attach Notification 34 to the User 2's Event 4, e.g., appendinga “System Confirmed” to the Event 4 title.

At Step 314, the System 1 scans the user's calendar Events 4 or emailmessages for information relating to upcoming Calls 14, such as AttendeePhone Numbers 5, passcodes or PINs 7 for conference calls, or identityof telecom Providers 6. The System 1 also scans for references tocall-related software, such as Skype and corresponding user names aswell as Email Addresses 17 of Attendees 16. If the System 1 finds suchinformation at Step 316, then at Step 318, the System 1 determineswhether the information matches information stored in the SystemDatabase 9. Certain information may be determined to be required tocreate a call Event 4, which may include Attendee Phone Number 5,passcode or PIN 7, or Provider 6. If System 1 finds Email Address(es) 17of Attendee(s) 16, then in Step 116 these Email Addresse(s) 17 are sentEmail(s) 18 through the System 1's API 33 to capture New User(s) 30.

If one or more required items are missing or are not recognized by theSystem Database 9, then the Event 4 may be sent to an Unknown CallsDatabase 11 at Step 324 that may be monitored by Human Agent 12 who maymanually create or edit the Event 4 in Step 326 by retrieving said datawithin Event 4 and System Database 9 and then placing the call inScheduled Call Queue 13. If the Human Agent 12 does not find some or allof the pertinent information and deciphers that Event 4 is not a Call14, then at Step 328 the Human Agent 12 manually discards the call. IfSystem 1 finds Email Address(es) 17 of Attendee(s) 16, then in Step 116these Email Addresse(s) 17 are sent Email(s) 18 through the System 1'sAPI 33 to capture New User(s) 30.

Human Agent 12 manually edits the call information to ensure the callwill be bridged correctly at Step 330. Once all pertinent data ismatched from System Database 9 and Event 4, the Call 14 is placed inScheduled Call Queue 13 at Step 332. Prior to Call 14, System 1 maygenerates a compatible DTMF Tone 25, or related information allowingSmartphone 36 to generate compatible DTMF Tone 25, for Smartphone 36 inStep 334. In Step 336 System 1 sends the DTMF Tone 25 or relatedinformation to Smartphone 36 via Notification 37. User 2 taps onNotification 37 which then launches Application 38 on Smartphone 36 inStep 338. Application 38 presents User 2 with prompt to Link 39. Byclicking on Link 39 within Application 38, User 2 can dial into thescheduled Call 14 via Link 39 at their own discretion, rather than beingbridged by System 1 at the exact time of Call 14. Once Link 39 isclicked in Step 340, Application 38 sends the DTMF Tone 25 to Smartphone36's dialer, and the Call 14 is dialed during Step 342. At Step 344 theUser 2 is placed using Smartphone 36's service provider which connectsthe User 2 to the selected Provider 6. Once the User 2 is connected toProvider 6, then Call 14 is bridged successfully at Step 344.

FIG. 6 shows a general purpose computer on which the system and methodof the present disclosure may be implemented. The computer system 900may execute at least some of the operations described above. Computersystem 900 may include processor 910, memory 920, storage device 930,and input/output devices 940. Some or all of the components 910, 920,930, and 940 may be interconnected via system bus 950. Processor 910 maybe single or multi-threaded and may have one or more cores. Processor910 may execute instructions, such as those stored in memory 920 or instorage device 930. Information may be received and output using one ormore input/output devices 940.

Memory 920 may store information and may be a computer-readable medium,such as volatile or non-volatile memory. Storage device 930 may providestorage for system 900 and may be a computer-readable medium. In variousaspects, storage device 930 may be a flash memory device, a floppy diskdevice, a hard disk device, an optical disk device, or a tape device.

Input/output devices 940 may provide input/output operations for system900. Input/output devices 940 may include a keyboard, pointing device,and microphone. Input/output devices 940 may further include a displayunit for displaying graphical user interfaces, speaker, and printer.External data, such as financial data, may be stored in accessibleexternal databases 960.

The features described may be implemented in digital electroniccircuitry, or in computer hardware, firmware, software, or incombinations thereof. The apparatus may be implemented in a computerprogram product tangibly embodied in an information carrier, e.g., in amachine-readable storage device or in a propagated signal, for executionby a programmable processor; and method steps may be performed by aprogrammable processor executing a program of instructions to performfunctions of the described implementations by operating on input dataand generating output.

The described features may be implemented in one or more computerprograms that are executable on a programmable system including at leastone programmable processor coupled to receive data and instructionsfrom, and to transmit data and instructions to, a data storage system,at least one input device, and at least one output device. A computerprogram may include set of instructions that may be used, directly orindirectly, in a computer to perform a certain activity or bring about acertain result. A computer program may be written in any form ofprogramming language, including compiled or interpreted languages, andit may be deployed in any form, including as a stand-alone program or asa module, component, subroutine, or other unit suitable for use in acomputing environment.

Suitable processors for the execution of a program of instructions mayinclude, by way of example, both general and special purposemicroprocessors, and the sole processor or one of multiple processors ofany kind of computer. Generally, a processor may receive instructionsand data from a read only memory or a random access memory or both. Sucha computer may include a processor for executing instructions and one ormore memories for storing instructions and data. Generally, a computermay also include, or be operatively coupled to communicate with, one ormore mass storage devices for storing data files; such devices includemagnetic disks, such as internal hard disks and removable, disks;magneto-optical disks; and optical disks. Storage devices suitable fortangibly embodying computer program instructions and data may includeall forms of non-volatile memory, including by way of examplesemiconductor memory devices, such as EPROM, EEPROM, and flash memorydevices; magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor andthe memory may be supplemented by, or incorporated in, ASICs(application-specific integrated circuits).

To provide for interaction with a user, the features may be implementedon a computer having a display device such as a CRT (cathode ray tube)or LCD (liquid crystal display) monitor for displaying information tothe user and a keyboard and a pointing device such as a mouse or atrackball by which the user may provide input to the computer.

The features may be implemented in a computer system that includes aback-end component, such as a data server, or that includes a middlewarecomponent, such as an application server or an Internet server, or thatincludes a front-end component, such as a client computer having agraphical user interface or an Internet browser, or any combination ofthem. The components of the system may be connected by any form ormedium of digital data communication such as a communication network.Examples of communication networks may include, e.g., a LAN, a WAN, andthe computers and networks forming the Internet.

The computer system may include clients and servers. A client and servermay be remote from each other and interact through a network, such asthe described one. The relationship of client and server may arise byvirtue of computer programs nmning on the respective computers andhaving a client-server relationship to each other.

Numerous additional modifications and variations of the presentdisclosure are possible in view of the above teachings. It is thereforeto be understood that within the scope of the appended claims, thepresent disclosure may be practiced other than as specifically describedherein.

Persons having skill in the art will realize that the invention can beadapted beyond the specific steps and interface elements set forthherein, and that small variations in method steps, user interfaces, orother aspects of the invention, including omission of certain methodsteps, can be immaterial. Persons having skill in the art will realizethat the invention can be practiced with a general purpose computerinstead of a touch screen portable device without deviating from thescope of the invention.

The invention claimed is:
 1. A computer system for connecting a user toa scheduled call, comprising: a processor in communication withnon-volatile memory, the non-volatile memory comprising: code forreceiving a user phone number where the user may be contacted andinformation allowing access to the user's calendar or email; code foraccessing the user's calendar or email and identifying the scheduledcall in the user's calendar or email, the scheduled call havinginformation including at least a scheduled call number and a scheduledcall time; code for placing a call to the scheduled call number beforethe scheduled call time; code for placing a call to the user at the userphone number before the scheduled call time; code for confirming theuser has answered the call to the user; and code for connecting the callto the user to the call to the scheduled call number, further code foralerting a human agent and receiving input from the human agent upondetection of an error condition while processing the scheduled callinformation after accessing the user's calendar or email.
 2. The systemof claim 1, wherein the scheduled call information further includes oneor more scheduled call access codes, and wherein code for placing thecall to the scheduled call number further includes transmitting soundscorresponding to the scheduled call access codes.
 3. The system of claim1, further comprising: code for identifying one or more characteristicsof the scheduled call including a provider associated with the scheduledcall; code for accessing a database storing requirements of theprovider; and wherein code for placing the call to the scheduled callnumber further includes transmitting sounds based on the requirements ofthe provider.
 4. The system of claim 3, wherein the sounds include oneor more of DTMF tones and text-to-speech.
 5. The system of claim 1,further comprising: code for prompting the user to state their name,recording the user's name, and transmitting the recorded user's name inresponse to a prompt when placing the call to the scheduled call number.6. The system of claim 1, further comprising: code fir updating theuser's calendar to include a notifier indicating the scheduled call hasbeen identified.
 7. The system of claim 1, further comprising: code fornotifying the user that the scheduled call has been identified.
 8. Acomputer system for connecting a user to a scheduled call, comprising: aprocessor in communication with non-volatile memory, the non-volatilememory comprising: code for receiving user information and informationallowing access to the user's calendar or email; code for accessing theuser's calendar or email and identifying the scheduled call in theuser's calendar or email, the scheduled call having informationincluding at least a scheduled call number and a scheduled call time;code for placing a call to the scheduled call number before thescheduled call time; and code for receiving a call from the user andconnecting the call from the user to the call to the scheduled callnumber, further code for alerting a human agent and receiving input fromthe human agent upon detection of an error condition while processingthe scheduled call information after accessing the user's calendar oremail.
 9. The system of claim 8, wherein the scheduled call informationfurther includes one or more scheduled call access codes, and whereincode for placing the call to the scheduled call number further includestransmitting sounds corresponding to the scheduled call access codes.10. The system of claim 8, further comprising: code for identifying oneor more characteristics of the scheduled call including a providerassociated with the scheduled call; code for accessing a databasestoring requirements of the provider; and wherein code for placing thecall to the scheduled call number further includes transmitting soundsbased on the requirements of the provider.
 11. A computer system forconnecting a user to a scheduled call stored in the user's calendar oremail, comprising: a processor in communication with non-volatilememory, the non-volatile memory comprising: code for transmitting to aserver a user phone number where the user may be contacted andinformation allowing access to the user's calendar or email containingscheduled call information including at least a scheduled call numberand a scheduled call time; code for receiving information from theserver to access the scheduled call; code for receiving from the serverand displaying to the user a notification that the scheduled call willbegin; and code for receiving input from the user and dialing into thescheduled call using information received from the server to access thescheduled call, further code for alerting a human agent and receivinginput from the human agent upon detection of an error condition whileprocessing the scheduled call information after accessing the user'scalendar or email.
 12. The computer system of claim 11, wherein theinformation from the server to access the scheduled call includes atleast a portion of the scheduled call information.
 13. The computersystem of claim 11, wherein the information from the server to accessthe scheduled call includes the scheduled call number.